Translation Source string Target string
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Anaconda Logging
Anaconda Logging
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Yohaan Vakil; Frank Sträter ; Ben Cotton
Yohaan Vakil; Frank Sträter ; Ben Cotton
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Introduction
Introduction
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Portuguese (Brazil)
Introduction
Introdução
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Korean
Introduction
안내
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Anaconda tracks all of its activities in logs. This includes:
Anaconda tracks all of its activities in logs. This includes:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
changing installation steps (that roughly correspond to different screens in the graphical installer)
changing installation steps (that roughly correspond to different screens in the graphical installer)
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
storage devices detection and manipulation
storage devices detection and manipulation
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
installation media detection
installation media detection
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
network initialization
network initialization
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
kernel messages
kernel messages
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
calls to critical methods within anaconda
calls to critical methods within anaconda
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
calls to external programs
calls to external programs
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Logging on the installed system
Logging on the installed system
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
During the installation the logs are stored in the `/tmp` directory:
During the installation the logs are stored in the `/tmp` directory:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Log files
Log files
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/tmp/anaconda.log`
`/tmp/anaconda.log`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
the general installation information, particularly the step changes.
the general installation information, particularly the step changes.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/tmp/storage.log`
`/tmp/storage.log`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
storage devices scan and manipulation (hard drives, partitions, LVM, RAID), partitioning
storage devices scan and manipulation (hard drives, partitions, LVM, RAID), partitioning
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/tmp/program.log`
`/tmp/program.log`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
calls to external programs, their output
calls to external programs, their output
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/tmp/packaging.log`
`/tmp/packaging.log`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
xref:dnf.adoc[DNF] package installation messages
xref:dnf.adoc[DNF] package installation messages
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/tmp/syslog`
`/tmp/syslog`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
hardware-related system messages
hardware-related system messages
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Certain log messages are also written to the terminals:
Certain log messages are also written to the terminals:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
TTY devices
TTY devices
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/dev/tty3`
`/dev/tty3`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
messages from `anaconda.log`, `storage.log` and `packaging.log`.
messages from `anaconda.log`, `storage.log` and `packaging.log`.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/dev/tty4`
`/dev/tty4`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
same as `syslog`
same as `syslog`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/dev/tty5`
`/dev/tty5`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
stdout and stderr from external programs +
stdout and stderr from external programs +
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`tty3` and `tty4` reflect certain log files. Log files always contain messages from all the loglevels, including debug, but the minimal loglevel on the terminals can be controlled with the `loglevel` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-loglevel[command line option].
`tty3` and `tty4` reflect certain log files. Log files always contain messages from all the loglevels, including debug, but the minimal loglevel on the terminals can be controlled with the `loglevel` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-loglevel[command line option].
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
There are two other log files created on the target filesystem, in the `/root` directory, also accessible at `/mnt/sysimage/root` during the installation:
There are two other log files created on the target filesystem, in the `/root` directory, also accessible at `/mnt/sysimage/root` during the installation:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/mnt/sysimage/root/install.log`
`/mnt/sysimage/root/install.log`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
log of the package installation process.
log of the package installation process.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`/mnt/sysimage/root/install.log.syslog`
`/mnt/sysimage/root/install.log.syslog`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
messages from installation chroot logged through the system's syslog.
messages from installation chroot logged through the system's syslog.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Mostly information about users and groups created during dnf's package installation.
Mostly information about users and groups created during dnf's package installation.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Log format
Log format
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
In files the format of the log messages is as follows:
In files the format of the log messages is as follows:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
H:M:S,ms LOGLEVEL facility:message
H:M:S,ms LOGLEVEL facility:message
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
where:
where:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Korean
where:
장소:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`H:M:S` is the message timestamp
`H:M:S` is the message timestamp
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`ms` is the millisecond part of timestamp. Note that this will usually become zero on a remote syslog.
`ms` is the millisecond part of timestamp. Note that this will usually become zero on a remote syslog.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`LOGLEVEL` is the message loglevel. In theory, because kernel messages are part of anaconda logs, all loglevels that are defined in rsyslog can appear in the logfiles. Anaconda itself will however log only at the following loglevels:
`LOGLEVEL` is the message loglevel. In theory, because kernel messages are part of anaconda logs, all loglevels that are defined in rsyslog can appear in the logfiles. Anaconda itself will however log only at the following loglevels:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`DEBUG`
`DEBUG`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`INFO`
`INFO`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`WARN`
`WARN`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`ERR`
`ERR`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`CRIT`
`CRIT`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`facility` is the program or component that created the message. Could be for instance `kernel`, `anaconda`, `storage` or similar.
`facility` is the program or component that created the message. Could be for instance `kernel`, `anaconda`, `storage` or similar.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`message` is the log message itself.
`message` is the log message itself.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
For the logs running in terminals, the format simply is:
For the logs running in terminals, the format simply is:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
LOGLEVEL facility:message
LOGLEVEL facility:message
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Remote logging via TCP
Remote logging via TCP
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Anaconda supports remote logging handled through the rsyslog daemon running on the installed system. It can be configured to forward its logs through TCP to an arbitrary machine in network that is also running a syslog daemon. This is controlled with the `syslog` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-syslog[command line option].
Anaconda supports remote logging handled through the rsyslog daemon running on the installed system. It can be configured to forward its logs through TCP to an arbitrary machine in network that is also running a syslog daemon. This is controlled with the `syslog` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-syslog[command line option].
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Do not forget to enable the port you are running your local syslog daemon on in your firewall.
Do not forget to enable the port you are running your local syslog daemon on in your firewall.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
What is logged remotely
What is logged remotely
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Everything that is logged directly by anaconda should also appear in the remote logs. This includes messages emitted by the loader and the storage subsystem. All anaconda tracebacks (/tmp/anaconda-tb-xyz) are concatenated into a single file /tmp/anaconda-tb-all.log and then transferred. Also, /tmp/x.log is transferred.
Everything that is logged directly by anaconda should also appear in the remote logs. This includes messages emitted by the loader and the storage subsystem. All anaconda tracebacks (/tmp/anaconda-tb-xyz) are concatenated into a single file /tmp/anaconda-tb-all.log and then transferred. Also, /tmp/x.log is transferred.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
The remote logging only works when the installer initializes network. Once network is up, it takes a couple of minutes for rsyslogd to realize this. Rsyslog has a queue for messages that couldn't be forwarded because of inaccessible network and it eventually forwards all of them, in the correct order.
The remote logging only works when the installer initializes network. Once network is up, it takes a couple of minutes for rsyslogd to realize this. Rsyslog has a queue for messages that couldn't be forwarded because of inaccessible network and it eventually forwards all of them, in the correct order.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Configuration
Configuration
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Spanish
Configuration
Configuración
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Portuguese (Brazil)
Configuration
Configuração
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Korean
Configuration
구성
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
It's up to you how the remote logging daemon is configured, you can for instance log all incoming messages into one file or sort them into directories according to the IP address of the remote system.
It's up to you how the remote logging daemon is configured, you can for instance log all incoming messages into one file or sort them into directories according to the IP address of the remote system.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
The anaconda RPM provides the `analog` script, which generates a suitable rsyslogd configuration file based on a couple of install parameters.
It is also able to generate a bash command to launch rsyslogd with the generated configuration.
Thus you can do from a shell:
`$ eval scripts/analog -p 6080 -s -o ./someconf /home/akozumpl/remote_inst`
This starts an rsyslog daemon that will listen on port 6080.
The logs from the remote machine with IP 10.34.33.221 will be stored under `/home/akozumpl/remote_inst/10.34.33.221/`, e.g. `/home/akozumpl/remote_inst/10.34.33.221/anaconda.log`.
The anaconda RPM provides the `analog` script, which generates a suitable rsyslogd configuration file based on a couple of install parameters.
It is also able to generate a bash command to launch rsyslogd with the generated configuration.
Thus you can do from a shell:
`$ eval scripts/analog -p 6080 -s -o ./someconf /home/akozumpl/remote_inst`
This starts an rsyslog daemon that will listen on port 6080.
The logs from the remote machine with IP 10.34.33.221 will be stored under `/home/akozumpl/remote_inst/10.34.33.221/`, e.g. `/home/akozumpl/remote_inst/10.34.33.221/anaconda.log`.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
The remote syslog configuration exploits several log message characteristics to be able to sort them into the correct files:
The remote syslog configuration exploits several log message characteristics to be able to sort them into the correct files:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
the IP of the message sender to know which machine generated the message and thud what directory does the message belong to.
the IP of the message sender to know which machine generated the message and thud what directory does the message belong to.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`anaconda.log, storage.log` and `program.log` have the name embedded in them as `programname`.
`anaconda.log, storage.log` and `program.log` have the name embedded in them as `programname`.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`syslog` messages are coming in from kernel and daemon facilities, just like they do on the installed system
`syslog` messages are coming in from kernel and daemon facilities, just like they do on the installed system
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`install.log.syslog` made during package installation is logged as a special `sysimage` hostname.
`install.log.syslog` made during package installation is logged as a special `sysimage` hostname.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Run `analog` without the `-o` option to see how exactly does a fitting configuration file look like. Also notice that it uses the same message format for remote logging as anaconda does, but you can of course modify this to specify any format you want.
Run `analog` without the `-o` option to see how exactly does a fitting configuration file look like. Also notice that it uses the same message format for remote logging as anaconda does, but you can of course modify this to specify any format you want.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
See also
See also
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Korean
See also
또한 보세요
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
link:https://www.rsyslog.com/doc/master/index.html[Rsyslog documentation]
link:https://www.rsyslog.com/doc/master/index.html[Rsyslog documentation]
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
`man tailf`
`man tailf`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Remote logging via virtio
Remote logging via virtio
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
QEMU/KVM in Fedora 13 and onwards allows one to create virtual machines with link:https://fedoraproject.org/wiki/Features/VirtioSerial[multiple virtio char devices] exposed to the guest machine. One such device can be used to forward anaconda logs to the host machine. In that way we can get logs forwarded in real time, as soon the anaconda logging subsystem is initialized (early) and not need to wait for the network to come up. Also, it's the only way to forward the logs in a no-network setup.
QEMU/KVM in Fedora 13 and onwards allows one to create virtual machines with link:https://fedoraproject.org/wiki/Features/VirtioSerial[multiple virtio char devices] exposed to the guest machine. One such device can be used to forward anaconda logs to the host machine. In that way we can get logs forwarded in real time, as soon the anaconda logging subsystem is initialized (early) and not need to wait for the network to come up. Also, it's the only way to forward the logs in a no-network setup.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Remote Logging Configuration
Remote Logging Configuration
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Anaconda will be forwarding logs over virtio automatically if it is able to find the port `/dev/virtio-ports/org.fedoraproject.anaconda.log.0"`. This is port is created using a libvirt XML directive that wires it to a TCP socket on the host's side. It's then possible to read the logs from there directly, or make an rsyslog instance to parse them and file them into respective files. See the ascii chart below for the whole ensemble:
Anaconda will be forwarding logs over virtio automatically if it is able to find the port `/dev/virtio-ports/org.fedoraproject.anaconda.log.0"`. This is port is created using a libvirt XML directive that wires it to a TCP socket on the host's side. It's then possible to read the logs from there directly, or make an rsyslog instance to parse them and file them into respective files. See the ascii chart below for the whole ensemble:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Anaconda--->rsyslog(guest)--->virtio(guest char device)--->kvm hypervisor--->virtio(TCP socket)
|
v
forwarded log files<---rsyslog(host)
Anaconda--->rsyslog(guest)--->virtio(guest char device)--->kvm hypervisor--->virtio(TCP socket)
|
v
forwarded log files<---rsyslog(host)
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Step by step instructions to set everything up follow:
Step by step instructions to set everything up follow:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Create a testing virtual machine, e.g. using Virtual Manager </li>
Create a testing virtual machine, e.g. using Virtual Manager </li>
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Add the virtio-serial port to your virtual machine, direct it to the TCP port 6080 on the host. Start by editing the guest configuration:`virsh edit <machine name>`
Add the virtio-serial port to your virtual machine, direct it to the TCP port 6080 on the host. Start by editing the guest configuration:`virsh edit <machine name>`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
In the guest editor, add following information into the `<devices>` section:
In the guest editor, add following information into the `<devices>` section:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
<channel type='tcp'>
<source mode='connect' host='127.0.0.1' service='6080'/>
<target type='virtio' name='org.fedoraproject.anaconda.log.0'/>
</channel>
<channel type='tcp'>
<source mode='connect' host='127.0.0.1' service='6080'/>
<target type='virtio' name='org.fedoraproject.anaconda.log.0'/>
</channel>
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Start the listening rsyslogd process on the host, using the `analog` script described [[#Remote_logging_via_TCP|above]]:
Start the listening rsyslogd process on the host, using the `analog` script described [[#Remote_logging_via_TCP|above]]:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
eval `analog -p 6080 -o rsyslogd.conf -s /home/akozumpl/remote_inst`
eval `analog -p 6080 -o rsyslogd.conf -s /home/akozumpl/remote_inst`
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Start the virtual machine.
Start the virtual machine.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Portuguese (Brazil)
Start the virtual machine.
Inicie a máquina virtual.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Continue with the installation. Immediately after the Anaconda greeting is displayed the log messages will appear in the directory given to `analog` script, in the `127.0.0.1` subdirectory.
Continue with the installation. Immediately after the Anaconda greeting is displayed the log messages will appear in the directory given to `analog` script, in the `127.0.0.1` subdirectory.
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
virt-install
virt-install
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — Spanish
virt-install
virt-install
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
If you are using virt-install you can configure it with the --channel option:
If you are using virt-install you can configure it with the --channel option:
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
--channel tcp,host=127.0.0.1:6080,mode=connect,target_type=virtio,name=org.fedoraproject.anaconda.log.0
--channel tcp,host=127.0.0.1:6080,mode=connect,target_type=virtio,name=org.fedoraproject.anaconda.log.0
fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English
Known issues and troubleshooting
Known issues and troubleshooting